fix(ogc): raise on an unreadable date bound instead of dropping the filter - #441

…ts (#442)

* feat(ogc): accept date, datetime and Timestamp values in date arguments

A datetime.date, datetime.datetime or pandas.Timestamp passed to a date
argument (time=[df.index.min(), None]) failed inside the formatter with
AttributeError ('endswith') or, for a lone datetime, TypeError (not
iterable), naming no argument. Read them like the equivalent string:
aware values convert to UTC, naive ones use the local zone as naive
strings do, a date is midnight of that day, and NaT is an open bound.
Any other type raises ValueError naming the argument.

Follow-up named in #441.

* fix(ratings): accept a lone date or Timestamp in get_ratings(time=...)

_validate_time_no_duration iterated a lone Timestamp/date and raised
TypeError before the formatter could read it; it now normalizes with
_coerce_to_list and checks only string elements.

Also:
- drop the redundant date check in _coerce_to_list (a date is not
  iterable), and update the Mapping TypeError to name the accepted types;
- read a bytes value as one element, so it gets the message naming the
  accepted types rather than "takes at most 2 values" over its byte codes;
- get_ratings' time docstring names the accepted date types;
- tighten the NEWS entry and date it by its land, above #446's.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HBt3Ee7eneKtdKQWq2T3YK

---------

Co-authored-by: thodson-usgs <thodson@usgs.gov>
Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

…st form (#443)

* fix(ogc): read each side of a "start/end" interval string like the list form

_format_api_dates sent any single string containing "/" unchanged. The
same range spelled as the documented string ("2024-01-01T10:00:00/..")
and as the list (["2024-01-01T10:00:00", None]) could select different
data: the string skipped the local-to-UTC conversion of naive times, the
offset-to-Z conversion, and the date truncation for date-only
collections, and "not-a-date/also-bad" reached the service unvalidated.

Split the string on its "/" and format each side as a list element is
formatted, so an unreadable side raises ValueError naming the caller's
argument before any request. An empty side becomes "..", and "../.."
means no filter, as [None, None] does. One side may still be an ISO 8601
duration paired with an instant ("2024-01-01/P7D"), kept unchanged; any
other shape (three sides, two durations, a duration with an open end)
raises ValueError naming the argument. A lone duration ("P7D") is
unchanged.

Follow-up named in #441.

* fix(ogc): reject duration sides, open starts per API, naive dates as UTC

- Reject a duration as either side of an interval string. The Water Data
  and NGWMN services reject '2024-01-01/P7D' and 'P7D/2024-01-08' with
  HTTP 400, and that error does not name the argument. _split_interval
  raises instead and passes the two sides to the list path as a tuple,
  which removes the duration handling in _format_interval and the
  _is_passthrough helper.
- Write an open range start in the form each API accepts. The NGWMN and
  STAC firewalls reject any datetime containing '../' with HTTP 403, so
  get_water_level(datetime=[None, end]) and get_ratings(time=[None, end])
  always failed. The Water Data API accepts '../end' and rejects '/end'
  with HTTP 400. OgcDialect.open_start holds the form (default '..');
  NGWMN sets '', and get_ratings passes '' to _format_api_dates because
  STAC has no dialect.
- Keep fractional seconds instead of truncating them, which changed a
  closed bound. The Water Data, NGWMN, and STAC services all accept them
  (checked 2026-10-12). Accept a minute-precision time and spaces around
  the '/'; both were previously sent unchanged and worked.
- Read a naive date or time as UTC, as pandas does and as
  get_nearest_continuous already did, instead of as the machine's local
  time. Convert an aware value to UTC, including in a date-only
  collection. Now that the string form is parsed like the list form,
  local time would have made time="2024-03-01/2024-03-02", the example
  in the docs, start at 06:00Z in Chicago and on the previous day in
  Sydney.
- Docstrings: get_ratings no longer says time is passed through
  unchanged, and the _format_api_dates notes describe open_start. The
  duration test ids name the side that is a duration.
- Date the NEWS entry by the day it lands and place it above #446's.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HBt3Ee7eneKtdKQWq2T3YK

---------

Co-authored-by: thodson-usgs <thodson@usgs.gov>
Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>